home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20030409-20031118
/
000021_toralf-delete-…@procaptura.com_Mon Apr 28 09:21:49 EDT 2003.msg
< prev
next >
Wrap
Text File
|
2003-11-18
|
4KB
|
78 lines
Article: 14237 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!phl-feed.news.verio.net!iad-feed.news.verio.net!iad-peer.news.verio.net!news.verio.net!newsfeed.icl.net!newsfeed.fjserv.net!skynet.be!skynet.be!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed1.e.nsc.no!nsc.no!nextra.com!news2.e.nsc.no.POSTED!53ab2750!not-for-mail
From: Toralf Lund <toralf-delete-this@procaptura.com>
Subject: Re: Communication protocol for direct serial link (null-modem or similar)?
Newsgroups: comp.protocols.misc,comp.protocols.kermit.misc
Organization: ProCaptura AS
References: <3R6qa.6946$b71.104830@news4.e.nsc.no> <b8bdvn$iun$1@watsol.cc.columbia.edu>
User-Agent: Pan/0.11.4 (Unix)
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Comment-To: "Frank da Cruz" <fdc@columbia.edu>
Lines: 56
Message-ID: <n05ra.7849$8g5.113401@news2.e.nsc.no>
NNTP-Posting-Host: 193.214.130.21
X-Complaints-To: news-abuse@telenor.net
NNTP-Posting-Date: Mon, 28 Apr 2003 09:47:31 MEST
X-Trace: news2.ulv.nextra.no 1051516051 193.214.130.21
Date: Mon, 28 Apr 2003 09:47:31 +0200
Xref: newsmaster.cc.columbia.edu comp.protocols.misc:9757 comp.protocols.kermit.misc:14237
On Fri, 25 Apr 2003 15:42:15 +0200, Frank da Cruz wrote:
> In article <3R6qa.6946$b71.104830@news4.e.nsc.no>, Toralf Lund
> <toralf-delete-this@procaptura.com> wrote:
> : I'm looking for a protocol that may be used for simple communication
> : across a direct serial link - RS232 using null-modem cable or similar
> : - between a Linux host and a simple (old) IPC (Intelligent Peripheral
> : Controller) board.
> :
> : The IPC has no real OS, just a simple, custom kernel, and rather
> : limited development support, so the protocol needs to be simple to
> : implement. Also, the system is really low-end by today's standards -
> : it's has a 12.5Mhz MC68010 CPU and 1Mb RAM - so the runtime must be
> : fairly small and efficient.
> :
> : The link will be used only to send simple packets ("commands") to the
> : IPC, and status from the IPC back to the Linux system; there will be
> : no file transfers or anything.
> :
> : Protocols I've considered:
> : - Kermit
> : - AHDLC/LAPB (as utilised e.g. by PPP) - X/Y/Z-modem
> :
> : What would you people out there recommend choosing? And does anyone
> : know of any good example source code that may help me get started? I'm
> : primarily interested in a nice and isolated implementation of the
> : packet communication itself, i.e. source code without all the
> : additional bits normally found in comms packages, like UI operations,
> : file I/O, modem dial etc., which I don't need (and I don't want them
> : there to confuse everything.)
> :
> Embedded Kermit is exactly like that, except it's for transferring
> files, not sending simple messages:
>
> http://www.columbia.edu/kermit/ek.html
>
> If you treat a message as a file, then Kermit would be fine.
How would I do that? What does the "file" interface look like?
> You'd need
> to adapt E-Kermit to the IPC, but that's what it's designed for. Then
> use a regular Kermit version on whatever you are connecting to the IPC,
> such as Linux. The nice thing about Kermit is that you are not
> constrained when picking implementation platforms. You can switch from
> Linux to Windows to DOS to Solaris, etc, at any time:
>
> http://www.columbia.edu/kermit/
>
> Kermit is also appropriate because it was designed with unreliable
> serial ports in mind, and therefore expects transmission errors and
> recovers from them efficiently.
Yes, that would be the whole point, obviously.
--
- Toralf